--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
docs/en/nomadmesh-pages.md HEAD (b89dc9e6) Text, 3.09 KB
NomadNet page formats
MeshChatX serves pages from a Mesh Server page node and displays them in the Nomad Network browser. Pages are fetched with the Nomad path convention T383838/page/<filename>.
Supported filenames
┌───────────┬─────────────────────────────────────────────────────────┐
│ Extension │ Role │
├───────────┼─────────────────────────────────────────────────────────┤
│ T383838.mu │ Micron markup (NomadNet default) │
│ T383838.md │ Markdown with GitHub-flavored features via the renderer │
│ T383838.txt │ Plain text with escaped HTML and preserved whitespace │
│ T383838.html │ Static HTML with CSS only (see security below) │
└───────────┴─────────────────────────────────────────────────────────┘
If you add a page without a recognised extension, the server stores it as T383838.mu. Filenames with other extensions (for example T383838.exe) are rejected when saving through the API.
Plain text (T383838.txt)
Content is HTML-escaped and shown with pre-wrapped whitespace. There is no Markdown parsing on T383838.txt pages.
Markdown (T383838.md)
Not the same engine as chat. Conversations use the lightweight T383838MarkdownRenderer in the messaging UI. Nomad T383838.md pages use T383838marked with GFM-oriented rules plus sanitisation. Features and edge cases can differ between the two paths. Automated tests cover both.
Authoring tips:
• Use ATX headings with a hash and a space before the title, for example T383838# Title, T383838## Section, T383838#### Subsection.
• Fenced code blocks keep indentation.
• Off-mesh T383838http and T383838https links in rendered content are removed or restricted so the preview cannot drive external navigation without mesh-style URLs.
HTML (T383838.html)
• JavaScript is not executed. T383838script tags and event-handler attributes are stripped.
• External resources are blocked where possible. T383838@import and T383838url(...) pointing at T383838http://, T383838https://, or protocol-relative URLs are removed from CSS.
• Embedded T383838<style> blocks are kept. Rules that target T383838html or T383838body are rewritten to apply to the viewer root container.
• Links must be mesh-style (T383838: paths, 32-character hex prefixes, T383838/page/..., T383838/file/..., or T383838# fragments) or they are removed.
• Images only keep T383838data:image/... inline sources.
• The viewer uses a sans-serif font for HTML and Markdown so pages do not inherit Micron monospace chrome. Override colours and typography with your own CSS.
Mesh Server API
• T383838POST /api/v1/page-nodes/{node_id}/pages with T383838name and T383838content saves a page. Invalid extensions return HTTP 400 with a short message.
• Listed pages only include files with allowed extensions in the T383838pages/ directory.
Archives
Snapshots in Archives use the same rendering pipeline as the Nomad browser. The archived T383838page_path extension selects Micron, Markdown, text, or HTML handling. Exports keep the original extension when it is T383838.mu, T383838.md, T383838.txt, or T383838.html.
See also
• Nomad Network and Mesh Server for browsing and hosting workflows
• Architecture and design for where page nodes fit in the backend
• Default Nomad entry path remains T383838/page/index.mu unless you change the URL in the browser
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────